Methods, apparatus and articles for use in association with token

ABSTRACT

In some embodiments, a method comprises receiving a request from a customer to temporarily associate a token issued to the customer with a payment account associated with the customer, and temporarily associating the token with the payment account in response at least in part to the request. In some embodiments, a method comprises issuing a token to a customer before the token is associated with a payment account; and arranging for the customer to have an ability to request that the token be associated with a payment account and usable as a payment token. In some embodiments, a method comprises receiving a mapping associating an identifier of a token with a payment account; receiving the identifier from a point of sale system; and determining the payment account based at least in part on the mapping and the identifier received from the point of sale system. In some embodiments, apparatus comprises: a processing system to: receive a request from a customer to temporarily associate a token issued to the customer with a payment account associated with the customer, and temporarily associate the token with the payment account in response at least in part to the request. In some embodiments, apparatus comprises: a processing system to: receive a mapping associating an identifier of a token with a payment account; receive the identifier from a point of sale system; and determine the payment account based at least in part on the mapping and the identifier received from the point of sale system.

BACKGROUND

Proximity payment devices are in widespread use. A well known standardfor proximity payment devices has been promulgated by MasterCardInternational Incorporated, the assignee hereof, and is referred to as“PayPass”. A proximity payment device often includes a wirelesscommunication interface to transmit a payment account number and/orother information to a point of sale (POS) system. The wirelessinterface often includes a radio frequency identification circuit (RFIDIC) and an antenna to communicate with and/or receive a power signalfrom the POS system.

Some venues support proximity payment devices as a way to reduce theamount of cash that must be handled by the venue. Unfortunately, someattendees of a venue may not have a proximity payment device and/orother device that allows them to purchase goods and/or services withoutcash. Thus, a venue that supports proximity payment devices maynonetheless find that it handles more cash than may be desired.

To address the above and further reduce the amount of cash that must behandled, some venues have acquired the ability to incorporate aproximity payment device into a ticket to be issued to a customer andused to enter the venue. The proximity payment device is associated withthe customer's payment account and allows the customer to make purchasesat the venue without cash.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic block diagram of a venue and a system, accordingto some embodiments;

FIG. 2 is a part schematic plan view, part schematic block diagram of atoken, according to some embodiments;

FIG. 3A is a schematic block diagram of a point of sale system,according to some embodiments;

FIG. 3B is a schematic block diagram of a reader device, according tosome embodiments;

FIG. 4 is a schematic block diagram of a portion of a processing system,according to some embodiments;

FIG. 5A is a flow chart that illustrates a method, according to someembodiments;

FIG. 5B is a flow chart that illustrates a method, according to someembodiments;

FIG. 5C is a flow chart that illustrates a method, according to someembodiments; and

FIG. 6 is a block diagram of an architecture, according to someembodiments.

DETAILED DESCRIPTION

Notwithstanding the benefit of proximity payment devices, it has beendetermined that it may be undesirable to incorporate a proximity paymentdevice into a ticket to be issued to a customer.

For example, a person other than the customer may come into possessionof the ticket before it reaches the customer and may use or attempt touse the proximity payment device in unauthorized purchase transactions.Some may not be happy with this.

Moreover, if a family or close group of friends attend the venue, it maynot be appropriate for each person too carry an identical pre-determinedvalue on their card. However it may also not be acceptable for only onemember of the group to be able to purchase goods and services during theevent. One member of the group may wish to purchase food and beveragefor the whole group for example; however this may require them tocollect all the tickets from group members to pay for each mealindependently. Equally the cost of a larger ticket purchase (souvenir)may to need to be split over a number of cards if no card has sufficientvalue to pay for the item outright. Some may not be happy with this.

Consequently, other methods, apparatus and systems to facilitatecashless transactions at a venue are desired.

FIG. 1 is a schematic block diagram of a venue and a system that may beused in carrying out cashless transactions at the venue, in accordancewith some embodiments.

Referring to FIG. 1, a venue 10 may comprise a stadium, a theme park, aresort, a hotel, (or other man made facility), a city (or otherjurisdiction), a property and/or any other type of venue. The venue 10may be operated by a venue operator 100 and may serve as a location forone or more events and/or attractions 102. An event may comprise asporting event, a play (or other type of performance), a movie (or othertype of showing) and/or any other type of event. An attraction maycomprise a theme park ride, an historical item (or other items), food(or other type of goods or services), wildlife, a geological structureand/or any other type of attraction.

The venue 10 may include a plurality of seats, represented by seats104A-104B. In some embodiments, each of the plurality of seats 104A-104Bis associated with a respective one of a plurality of identifiers,represented by identifiers 106A-106B.

The venue 10 may further include concession areas, represented byconcession area 108. The concession areas 108 may be operated by one ormore merchants, represented by a merchant 110. Point of sale (POS)systems, represented by POS system 112, may be disposed in theconcession areas 108. Such POS systems 112 may be coupled to aprocessing system 114, which may be disposed inside and/or outside ofthe venue 110.

In some embodiments, processing system 114 is associated with amanagement entity. In some embodiments, such management entity comprisesthe venue operator 100 and/or the token issuer 140.

A communication link 116 may couple the processing system 114 to aprocessing system 118, which may in turn be associated with (e.g.,operated by and/or on behalf of) a financial institution 120.

The communication link 116 may comprise any type of communication link,for example, but not limited to wired (e.g., conductors, fiber opticcables) or wireless (e.g., acoustic links, electromagnetic links or anycombination thereof including, for example, but not limited to microwavelinks, satellite links, infrared links), and/or any combinationsthereof. A communication link may be public or private, dedicated and/orshared (e.g., a network) and/or any combination thereof. Thus, acommunication link may or may not be a permanent communication link. Acommunication link may support any type of information in any form, forexample, but not limited to, analog and/or digital (e.g., a sequence ofbinary values, i.e. a bit string) signal(s) in serial and/or in parallelform. The information may or may not be divided into blocks. If dividedinto blocks, the amount of information in a block may be predeterminedor determined dynamically, and/or may be fixed (e.g., uniform) orvariable. In some embodiments, communication link 116 comprises acomputer network 122. In some embodiments, the computer network 122comprises a payment processing network. In some embodiments, one or moreportions of a communication link employs a protocol or combination ofprotocols, for example, but not limited to, the Internet Protocol.

The processing system 114 may also be coupled to POS systems,represented by POS system 126, disposed outside of the venue 10. The POSsystems 126 may be disposed in concession areas, represented by aconcession area 128, and may be operated by one or more merchants,represented by a merchant 130.

The venue 10 may be attended by customers, represented by customers132A-132B. The customers 132A-132B may use a plurality of tokens,represented by tokens 134A-134D, in the course of attending the venue10. In some embodiments, each of the tokens 134A-134D comprises a ticketthat entitles a holder to enter the venue 10. One or more of the tokens134A-134D may entitle a holder to receive one or more other benefits.The other benefits may include a trip on a transit system, a ride in atheme park, and/or food and/or drink from a food and/or drink service.

Each of the plurality of tokens 134A- 134D may include an identifier,represented by identifiers 136A-136D, respectively. In some embodiments,each of the identifiers is unique in that it is different than allothers of the identifiers 136A-136D. In some embodiments, each of theplurality of tokens 134A-134D includes a device and/or machine readablemedium that stores the token's identifier. In some embodiments, thedevice and/or machine readable medium includes a magnetic strip, a barcode, and/or an integrated circuit. In some embodiments, a bar codecomprises a three dimension (3D) bar code. In some embodiments, each ofthe tokens 134A-134D further includes one or more security features thatallow the identity and authenticity of the token to be confirmed. Insome embodiments, the tokens may include one or more features that maybe utilized to support services such as cardholder age verificationand/or restricting entry to the venue 100 (or one or more portionsthereof).

A token issuer 140 may issue the tokens 134A-134D to the customers132A-132B. Unless stated otherwise, the term “issue to” may include, butis not limited to, give to, loan to, rent to, sell to, transfer toand/or provide to. The term “provide to” may include, but is not limitedto, hand to and/or send to. The term “send to” may include, but is notlimited to, mail to and/or ship to. In some embodiments, a plurality ofthe tokens, e.g., tokens 134A-134B, are issued to a single customer,family and/or a group, e.g., customer (or family or group) 132A.

In accordance with some embodiments, the tokens 134A-134D are notassociated with payment accounts prior to issuing the tokens 134A-134Dto the customers 132A-132B. In some embodiments, this helps to reducethe possibility of fraud.

The token issuer 140, venue operator 100 and/or a management entityassociated with the processing system 114 may arrange for a customer tohave an ability to request that one or more of the tokens 134A-134Dissued to the customer be temporarily associated with one or morepayment accounts and temporarily usable as payment tokens. In someembodiments, a payment account may comprise any type of payment account.In some embodiments, a payment account may comprise a pre-paid paymentaccount, a debit account or a credit account.

In some embodiments, neither the token issuer 140, the venue operator100, nor a management entity associated with the processing system 114are banks. Thus, the token issuer 140 and/or venue operator 100 maycontract with the financial institution 120 (or other entity that offerspayments accounts), which in turn may provide the customer with theability to request that one or more of the tokens 134A-134D issued tothe customer be temporarily associated with one or more payment accountsand temporarily usable as payment tokens. In some embodiments, the tokenissuer 140 and/or venue operator 110 may arrange for all of thecustomers 134A-134D to have such ability.

In some embodiments, the agreement may provide for the tokens 134A-134Dto operate in a manner that is the same as and/or similar to a standardbank card or product (e.g. PayPass).

In some embodiments, the financial institution 120 (or other entity thatoffers payments accounts) is not involved in issuing and/or maintainingthe tokens 134A-134D.

Thereafter, a customer issued one or more of the tokens 134A-134D mayrequest that one or more of such tokens be temporarily associated with apayment account and temporarily usable as a payment token. In someembodiments, the customer supplies the request via a website, atelephone, email, mail, in person, and/or using any other method. If thecustomer supplies the request via a website and/or email, the customermay employ one of computers 138A-138B, which may be coupled to theprocessing system 118. The one of computers 138A-138B may execute abrowser program and/or email program, receive signals from one or moreinput devices (e.g., a mouse and/or keyboard), and in response at leastin part thereto, forward the request via the website and/or email. Therequest may be forwarded to the processing system 118.

The customer may further supply criteria for using the token in apayment transaction, sometimes referred to as use criteria. In someembodiments, the customer supplies the use criteria via a website, atelephone, email, mail, in person, and/or any other method. The usecriteria may be forwarded to the processing system 118.

The processing system 118 and/or financial institution 120 may receivethe request and may temporarily associate the token with the paymentaccount in response at least in part to the request. This may includedefining a mapping that associates the token's identifier with thepayment account. The mapping may be supplied to the processing system114.

In some embodiments, the processing system 118 may temporarily associatethe token with the payment account only if the customer is associatedwith the payment account. Unless stated otherwise, the customer isassociated with the payment account if the customer is an account holderof such payment account and/or otherwise authorized to access and/or usethe payment account.

In some embodiments, temporarily associating the token with a paymentaccount comprises associating the token with the payment account for apredetermined time period. In some embodiments, the predetermined timeperiod is based at least in part on the date and time of an event at thevenue.

The processing system 118 and/or financial institution 120 may furtherreceive the use criteria.

In some embodiments, one or more of the other entities 100, 140, and/orone or more of the other systems 112, 114 may receive the request and/oruse criteria. In some such embodiments, the one or more other entities100, 140, and/or systems 112, 114 may temporarily associate the tokenwith the payment account. In some embodiments, the one or more otherentities 100, 140, and/or systems 112, 114 may instead forward therequest to the financial institution 120 and/or processing system.

Thereafter, the customer may use the token in a payment transaction. Insome embodiments, the customer carries this out by presenting the tokento one of the POS systems 112, 126. In some embodiments, the POS systemthereafter receives the token's identifier. As stated above, in someembodiments, each of the plurality of tokens 134A-134D includes a deviceand/or machine readable medium that stores the token's identifier. Insome embodiments, the device and/or machine readable medium includes amagnetic strip, a bar code, and/or an integrated circuit. In someembodiments, one or more portions of the “PayPass” standard areemployed.

The POS system may utilize one or more security features (if included)of a token to confirm the identity and/or authenticity of the token.

The POS system may thereafter supply the identifier to the processingsystem 114. In some embodiments, the processing system 114 determines apayment account associated with the identifier. In some embodiments, thepayment account is based at least in part on the identifier and amapping. The mapping may comprise the mapping 140.

In some embodiments, the payment account number comprises a PAN number.

In some embodiments, the processing system 114 may confirm the identityand/or authenticity of the token prior to determining the paymentaccount. This may be in addition to and/or in lieu of confirmation ofidentity and/or authenticity by the POS system.

In some embodiments, the identifier itself may be a payment accountnumber.

The processing system 114 may thereafter initiate a payment transactionassociated with the payment account. This may include communicating witha payment card system to initiate a payment transaction against thepayment account temporarily associated with the token. In someembodiments, the payment card system includes the processing system 118.

In some embodiments, the processing system 114 routes the paymentaccount number and data indicative of the transaction to an issuer ofthe payment account associated with the token. In some embodiments, theissuer of the payment account is the financial institution 120.

The processing system 118 may receive the request to authorize a paymenttransaction associated with the payment account. The processing system118 may thereafter determine whether to authorize the paymenttransaction. In some embodiments, this determination is based at leastin part on whether the use criteria is satisfied.

If the payment transaction is authorized, the processing system 118 mayprovide an authorization. In some embodiments, the authorization issupplied via a payment card system.

In some embodiments, an attendee may decide to attend an event carryingonly the token that has been temporarily associated with a paymentaccount. Thus, in some embodiments, the attendee's wallet, purse, cashand/or normal payment cards may be left at home.

In some embodiments, a pre-determined amount is transferred to suchtoken from the payment account. Any balance remaining after the event(and/or after the token is no longer associated with the paymentaccount) may be transferred back to the original funding source. In someembodiments, such transfer is automatic.

As stated above, in some embodiments, the tokens 134A-134D are onlytemporarily associated with the payment accounts, and thus the tokens134A-134D may be disposable and not intended to completely replace debitcards and/or credit cards.

In some embodiments, an entity that provides a service is compensatedfor the service provided by that entity. In some embodiments, eachentity that provides a service is compensated for the service providedby that entity.

In some embodiments, the financial institution 120 or other entity mayinitiate a charge for one or more services performed. In someembodiments, revenue from the charge is shared between two or moreentities. In some embodiments, such entities include the venue operator100, the token issuer 140 and/or the financial institution 120. In someembodiments, the portion of the revenue received by each particularentity is based on the one or more services provided by that entity. Insome embodiments, each entity that performs one or more of the servicesdescribed herein receives a portion of the revenue. In some embodiments,the portion of the revenue received by each particular entity is basedon the one or more services provided by that entity.

It should be noted that if the tokens 134A-134D do not operate in amanner that is the same as and/or similar to a standard bank card orproduct (e.g. PayPass), the tokens 134A-134D may be usable only atdesignated locations.

In some embodiments, it may be desirable to associate two or moretokens, e.g., tokens 134A-134B, of the plurality of tokens, e.g. tokens134A-134B, issued to a single customer, family and/or group, e.g.,customer (or family or group) 132A, with the same payment account. (Ifissued to a single customer, e.g., customer 132A, the customer maydistribute one or more token, e.g., token 134B, of the plurality oftokens, e.g., tokens 134A-134B, to one or more other members of thecustomer's family and/or group.) In some embodiments, this increases theusefulness (of the tokens) to the family and/or group. In someembodiments two or more tokens, e.g., tokens 134A-134B, of the pluralityof tokens, e.g. tokens 134A-134B, issued to the customer, family and/orgroup, e.g., customer (or family or group) 132A, may share apre-determined amount from the same payment account. In someembodiments, this further increases the usefulness (of the tokens) to afamily and/or group.

In some embodiments, the system may be used to limit the amount that afamily and/or group may spend at, and/or in association with, an eventand/or attraction, and may also limit their exposure to theft. In someembodiments, this may be particularly helpful if consumption ofalcoholic beverages is expected.

In some embodiment, additional services may be offered by the tokenissuer 140, venue operator 100 and/or management entity. In someembodiments, the management entity may offer immediate replacement offaulty and/or lost tokens within the venue. In some embodiments, themanagement entity may utilize one or more of features (if included) ofthe tokens to verify cardholder age and/or restrict entry to the venue(or one or more portions thereof). In some embodiments, the managemententity may provide services to authorize transactions (or consolidationof multiple small value transactions) on site to minimize transactiontimes and acquiring costs within the venue. In some embodiments, one ormore services provided by the management entity and/or one or more ofthe other entities may be designed to provide ‘high availability’ ofsystems during an event. In some embodiments, the POS systems 112, 126,the processing system 114, the processing system 118, and/or one or moreportions of the communication link 116 may provide greater bandwidthduring an event than at one or more other times.

FIG. 2 is a part schematic plan view, part schematic block diagram, ofone of the plurality of token 134A-134D, e.g., token 134A, according tosome embodiments. Referring to FIG. 2, in accordance with someembodiments, the token 134A includes a body 200 and regions 202-214. Thebody 200 may be generally card shaped. Regions 202-208 may includeindicia identifying a venue, an event and/or attraction, a date of theevent and/or attraction, and a time of the event and/or attraction,which collectively define the venue and event and/or attraction forwhich the holder is entitled to enter the venue. Regions 210-212 mayinclude indicia identifying a seat associated with the token and a costof the token. Region 214 may include one or more brand and/or logo of anissuer or a payment card association and/or one or more brand and/orlogo thereof.

The token 134A may further include a device 216 to store the identifier136A and/or supply the identifier 136A to a POS system 112, 126. In someembodiments, the device 216 includes a magnetic strip, a bar code,and/or an RFID IC or other integrated circuit. In the illustratedembodiment, the device 216 includes control/storage circuitry 218 and awireless communication interface 220. The control/storage circuitry 218may store the identifier 136A (and/or other information to be suppliedto the POS system 112, 126). The wireless communication interface 220may transmit the identifier 136A (e.g., in the form of signalsrepresenting the identifier 136A) and/or other information to the POSsystem 112, 126 and may receive signals from the POS system 112, 126.The signals received from the POS system 112, 126 may include aninterrogation signal, a power signal and/or other signals.

The control storage circuitry 218 may comprise any type ofcontrol/storage circuitry. For example, the control/storage circuitry218 may be programmable or non programmable, general purpose or specialpurpose, dedicated or non dedicated, distributed or non distributed,shared or not shared, and/or any combination thereof. Control/storagecircuitry may include, but is not limited to, hardware, software,firmware, and/or any combination thereof. Hardware may include, but isnot limited to off the shelf integrated circuits, custom integratedcircuits and/or any combination thereof. In some embodiments,control/storage circuitry comprises a microcontroller and/or any othertype of microprocessor. Software may include, but is not limited to,instructions that are storable and/or stored on a computer readablemedium, such as, for example, magnetic or optical disk, magnetic oroptical tape, CD-ROM, DVD, RAM, EPROM, ROM or other semiconductormemory. Control/storage circuitry may employ continuous signals,periodically sampled signals, and/or any combination thereof. Ifcontrol/storage circuitry is distributed, two or more portions of thecontrol/storage circuitry may communicate with one another through acommunication link.

In some embodiments, the control/storage circuitry 218 comprises asimple memory device capable only of responding to a pre-defined set ofcommands. In some other embodiments, the control/storage circuitry 218comprises a secure microcontroller capable of executing a pre-definedprogram.

The wireless communication interface 220 may comprise an antenna 222 andtransmit/receive circuitry 224. The antenna 222 may be configured totransmit and receive radio frequency (RF) signals and may comprise aloop antenna and/or any other suitable configuration. Thetransmit/receive circuitry 224 may be coupled between the antenna 222and the control/storage circuitry 218.

In some embodiments, the control/storage circuit 218 and thetransmit/receive circuitry 224 are disposed in a single integratedcircuit 226. In some embodiments, the single integrated circuit 226comprises an RFID IC. Unless stated otherwise, the term RFID is notlimited to a specific type of RFID. In some embodiments, an RFID is asimple memory device capable only of responding to a pre-defined set ofcommands. In some other embodiments, an RFID comprises a microcontrollercapable of executing a program. In some embodiments, an RFID ICcomprises an IC that uses contactless technology, such as, for example,as specified in international standard ISO/IEC 14443. Some embodimentsmay include additional features and/or other configurations altogether.

In operation, wireless signals (e.g., RF signals) may be received by theantenna 222 and supplied to the transmit/receive circuitry 224, which inresponse may provide signals that are supplied to the control/storagecircuitry 218. The control/storage circuitry 218 may also providesignals that are supplied to the transmit/receive circuitry 224, whichin response may provide signals that are supplied to the antenna 222 andtransmitted thereby.

In some embodiments, device 216 is supported by the body 200. Unlessstated otherwise, the term “supported by” may include but is not limitedto partially, and/or entirely, disposed on, disposed in, mounted on,mounted in, installed on, installed in, contained in and/or embedded in.

In some embodiments, the device 216 is the same as and/or similar todevices used to store account information and perform wirelesscommunication in proximity payment devices.

In some embodiments, the device 216 operates in accordance with theabove-mentioned “PayPass” standard.

The technology and security used in the token 134A may be the same as,or different from, that used in other types of payment devices of thesame brand and/or payment scheme.

FIG. 3A is a schematic block diagram of one of the POS systems 112, 126,according to some embodiments. Referring to FIG. 3A, in accordance withsome embodiments, the POS system 106 may include a reader device 302, aprocessor 304, an output device 306, a communication interface 308 and apower supply 310.

The reader device 302 receives the token identifier from the token. Ifthe identifier is stored in a magnetic strip, the reader device 302 maycomprise a magnetic strip reader. If the identifier is stored in a barcode, the reader device 302 may comprise a bar code reader. If theidentifier is stored in an integrated circuit, the reader device 302 maycomprise a proximity coupling device. In some embodiments, the readerdevice 302 comprises a proximity coupling device to perform wirelesscommunication with the device 216 (FIG. 2) that stores the identifier136A of token 134A. In some embodiments, the reader device 302 comprisesa proximity coupling device that is the same as and/or similar toproximity coupling devices used to receive account information fromproximity payment devices.

The processor 304 may comprise any type of processor. For example, aprocessor may be programmable or non programmable, general purpose orspecial purpose, dedicated or non dedicated, distributed or nondistributed, shared or not shared, and/or any combination thereof. Aprocessor may include, but is not limited to, hardware, software,firmware, and/or any combination thereof. Hardware may include, but isnot limited to off the shelf integrated circuits, custom integratedcircuits and/or any combination thereof. In some embodiments, aprocessor comprises a microprocessor. Software may include, but is notlimited to, instructions that are storable and/or stored on a computerreadable medium, such as, for example, magnetic or optical disk,magnetic or optical tape, CD-ROM, DVD, RAM, EPROM, ROM or othersemiconductor memory. A processor may employ continuous signals,periodically sampled signals, and/or any combination thereof. If aprocessor is distributed, two or more portions of the processor maycommunicate with one another through a communication link.

In operation, the reader device 302 may receive the identifier (e.g., inthe form of signals that represent the identifier) from a device and/ormachine readable medium storing such identifier, and/or transmit signalsto such device and/or machine readable medium. The reader device 302 mayalso receive signals from the processor 304 and/or transmit signals tothe processor 304. The processor 304 may receive signals from and/ortransmit signals to the reader device 302, the output device 304 and/orthe communication interface 310.

Although the reader device 302, the processor 304, the output device 306and the communication interface 310 are shown separate from one another,in some embodiments, the reader device 302, the processor 304, theoutput device 306 and/or the communication interface 310 may share oneor more circuits and/or other components.

The power source 310 may be coupled (directly and/or indirectly) and/orsupply power (directly and/or indirectly) to the reader device 302, theprocessor 304, the output device 306, and/or the communication interface308.

FIG. 3B is a schematic block diagram of a reader device 302, accordingto some embodiments. Referring to FIG. 3B, in accordance with someembodiments, the reader device 302 include may include control/storagecircuitry 318 and a wireless communication interface 320.

The control storage circuitry 318 may comprise any type ofcontrol/storage circuitry. In some embodiments, the control/storagecircuitry 318 comprises a simple memory device capable only ofresponding to a pre-defined set of commands. In some other embodiments,the control/storage circuitry 318 comprises a secure microcontrollercapable of executing a pre-defined program.

The wireless communication interface 320 may comprise an antenna 322 andtransmit/receive circuitry 324. The antenna 322 may be configured totransmit and receive radio frequency (RF) signals and may comprise aloop antenna and/or any other suitable configuration. Thetransmit/receive circuitry 324 may couple the antenna 322 to thecontrol/storage circuitry 318.

The wireless communication interface 320 may allow the reader device 302to transmit signals to and/or to receive signals from the device 216(FIG. 2) that stores the identifier 136A of token 134A.

In some embodiments, device 216 is within range of the reader device 302if a wireless communication interface 220 of the device 102 ispositioned in a field generated by the wireless communication interface320 of the reader device 302.

In operation, wireless signals (e.g., RF signals) may be received by theantenna 322 and supplied to the transmit/receive circuitry 324, which inresponse may provide signals that are supplied to the control/storagecircuitry 318. The control/storage circuitry 318 may also providesignals that are supplied to the transmit/receive circuitry 324, whichin response, may provide signals that are supplied to the antenna 322and transmitted thereby.

In some embodiments, the control/storage circuit 318 and thetransmit/receive circuitry 324 are disposed in a single integratedcircuit.

In some embodiments, the control/storage circuit 318 and thetransmit/receive circuitry 324 are disposed in an IC that uses NFCtechnology, such as, for example, an NFC IC compliant with ISO/IEC18092/ECMA-340 or ISO/IEC 21481/ECMA-352.

In some embodiments, the control/storage circuitry 318 and/or thewireless communication interface 320 are the same as and/or similar tocontrol/storage circuitry and/or a wireless communication interface usedto receive account information from proximity payment devices.

In some embodiments, the control/storage circuitry 318 and/or thewireless communication interface 320 are configured to allow theproximity coupling device 302 to operate in accordance with theabove-mentioned “PayPass” standard.

FIG. 4 is a schematic block diagram of data that may be stored in theprocessing system 118, in accordance with some embodiments. Referring toFIG. 4, in accordance with some embodiments, the processing system 118may include token data 400, account data 402 and use criteria 404.

The token data 400 may include a token identifier 410, a venueidentifier 412, an event identifier 414, and a date and a time 416. Insome embodiments, the token identifier 410, the venue identifier 412,the event identifier 414, the date and time 416 are combined into asingle identifier. The token data 402 may further include a second tokenidentifier 450.

The account data 402 may include an account number 420 associated with apayment account and other account information 422. In some embodiments,the other account information 422 includes an expiration date associatedwith the payment account.

The account data 402 may further include a second account number 424associated with a second payment account and other account information426. In some embodiments, the other account information 426 includes anexpiration date associated with the second payment account.

The use criteria 404 may include (i) data 430 indicative of goods and/orservices that may be purchased using the token, (ii) data 432 indicativeof goods and/or services that may not be purchase using the token, (iii)data 434 indicative of an amount that may be spent using the token, (iv)data 436 indication of a location at which purchases may be made usingthe token, (v) data 440 indicative of a start date and time to allowpurchases using the token, (vi) data 442 indicative of an end date andtime to allow purchases using the token, (vii) data 444 indicative ofcriteria for using the token to make purchases associated with thesecond payment account, and (viii) data 446 indicative of criteria forusing the token to make purchases associated with a payment accounttemporarily associated with the second token.

In some embodiments, the token is temporarily associated with paymentaccount from the start date and time until the end date and time. Insome embodiments, the token is not associated with the payment accountuntil the start date and time. In some embodiments, the token is nolonger associated with the payment account after the end date and time.

In some embodiments, one, some or all of the use criteria data elementshave a default value when the token is initially associated with apayment account. In some embodiments, the default value of a dataelement is defined by the customer. In some embodiments, the customerhas the ability to change the value of one or more of the data elements.

In some embodiments, the token data 400, the account data 402 and/or theuse criteria are stored in a single record.

In some embodiments, one or more of the data elements shown in FIG. 4are not used.

In some embodiments, the data 432 may indicate that alcohol may not bepurchased using the token.

In some embodiments, the data 436 indicates that purchases may be madeonly at locations in the venue. In some embodiments, the data 436indicates that purchases may be made only at locations in the venue andlocations within one block of the venue. In some embodiments, the data436 indicates that purchases may be made only at locations in the venueand locations within one mile of the venue.

In some embodiments, the data 440 indicates that the start date is thesame date as the date of the event, one day prior to the date of theevent or one week prior to the date of the event.

In some embodiments, the data 442 indicates that the end date is thesame date as the date of the event, one day after the date of the eventor one week after the date of the event.

In some embodiments, the start date and end date are the same as thedate of the event. In some such embodiments, the start time may be thesame as the start time of the event, one hour before the start time ofthe event, or any time less than three hours before the start time ofthe event. The end time may be the same as the end time of the event,one hour after the end time of the event, or any time less than threehours after the end time of the event.

In some embodiments, the tokens 134A-134D are only temporarilyassociated with the payment accounts, and thus the tokens 134A-134D maybe disposable and not intended to completely replace debit cards and/orcredit cards.

In some embodiments, two or more tokens, e.g., tokens 134A-134B, of theplurality of tokens, e.g. tokens 134A-134B, issued to the customer,family and/or group, e.g., customer (or family or group) 132A, may beassociated with the same payment account. In some embodiments, thisincreases the usefulness (of the tokens) to the family and/or group. Insome embodiments two or more tokens, e.g., tokens 134A-134B, of theplurality of tokens, e.g. tokens 134A-134B, issued to the customer,family and/or group, e.g., customer (or family or group) 132A, may sharea pre-determined amount from the same payment account. In someembodiments, this further increases the usefulness (of the tokens) to afamily and/or group. In some embodiments, the system may be used tolimit the amount that a family and/or group may spend at, and/or inassociation with, an event and/or attraction, and may also limit theirexposure to theft. In some embodiments, this may be particularly helpfulif consumption of alcoholic beverages is expected.

In some embodiments, the criteria for using one token, e.g., token 134A,of the plurality of tokens, e.g. tokens 134A-134B, issued to thecustomer, family and/or group, e.g., customer (or family or group) 132A,may be different than the criteria for using another token, e.g., token134B, of the plurality of tokens, e.g. tokens 134A-134B, issued to thecustomer, family and/or group, e.g., customer (or family or group) 132A.In some embodiments, for example, it may be expected that one of thetokens will be used by an adult in the family and/or group and the othertoken may be used by a child in the family and/or group.

In some embodiments, the processing system 118 may include similar datafor one, some or all other tokens of the plurality of tokens 134A-134D.

FIG. 5A is a flow chart 500 of a method according to some embodiments.In some embodiments, one or more portions of the method may be performedin association with one or more token, e.g., token 134A, of theplurality of tokens 134A-134D. In some embodiments, one or more portionsof the method may be performed by a token issuer 140 (FIG. 1). Themethod is not limited to the order shown in the flow chart. Rather,embodiments of the method may be performed in any order that ispracticable. For that matter, unless stated otherwise, any methoddisclosed herein may be performed in any order that is practicable.Notably, some embodiments may employ one or more portions of the methodwithout one or more other portions of the method.

At 502, the method may include providing a token having an identifier.In some embodiments, this includes defining an identifier to beassociated with the token and storing the identifier on the token. Insome embodiments, storing includes storing the identifier on a magneticstrip, a bar code and/or in control/storage circuitry 218 (FIG. 2).

In some embodiments, other token data is also defined and stored on thetoken. In some embodiments, the other token data includes a venueidentifier, an event identifier, a date and/or a time. In someembodiments, the token identifier, the venue identifier, the eventidentifier, the date and/or the time are combined into a singleidentifier. If tokens are processed as a batch, one or more portions ofthe token data may be the same for all tokens in the batch. In someembodiments, one or more portions of the token data are printed on thetoken.

In some embodiments, one or more portions of the defining, storingand/or printing are carried out in the course of fabricating the token.In some embodiments, one or more portions of the defining, storingand/or printing may be the same as and/or similar to one or moreportions of one or more methods used in personalization and/orpre-personalization of a proximity payment card. In some embodiments,one or more portions of the defining, storing and/or printing is carriedout using contactless programming equipment that is the same as and/orsimilar to contactless programming equipment commonly used to programproximity payment cards, such as for example, a model 9000 availablefrom Datacard Group, Minnetonka, Minn.

At 504, the method may further include issuing the token to a customer.In some embodiments, issuing the token to a customer comprises giving,loaning, renting, selling, transferring and/or providing the token tothe customer. Providing the token to the customer may include handingand/or sending the token to the customer. Sending the token to thecustomer may include mailing the token to the customer.

At 506, the method may further include arranging for the customer tohave an ability to request that the token be temporarily associated witha payment account and temporarily usable as a payment token. In someembodiments, this includes contracting with a financial institution toarrange for the financial institution to provide the customer with theability to request that the token be temporarily associated with apayment account and temporarily usable as a payment token.

The method may further include printing a notice regarding thearrangement. The notice may be issued to the customer.

At 508, the method may further include receiving a mapping associatingthe identifier with a payment account. In some embodiments, the mappingcomprises a mapping defined by a financial institution that provides thecustomer with the ability to request that the token be temporarilyassociated with a payment account and temporarily usable as a paymenttoken.

At 510, the method may further include receiving the identifier at a POSsystem. In some embodiments, the identifier is supplied by a tokenpresented to the POS system. In some embodiments, one or more portionsof the “PayPass” standard are employed. For example, the token may bepresented to the proximity coupling device and the proximity couplingdevice may transmit an interrogation signal in response at leastthereto. The token may receive the interrogation signal via an antenna206 (FIG. 2A). The interrogation signal may cause the circuitry of thetoken to be powered-up. For example, the token may include circuitry torectify the received interrogation signal to generate DC power that maybe used to power control/storage circuitry 218 (FIG. 2) andtransmit/receive circuitry 224 (FIG. 2).

The token may transmit one or more signals to the proximity couplingdevice in response to the interrogation signal. The one or more signalsmay be transmitted via the antenna 222 (FIG. 2) and may include tokendata and/or other information required for interaction with theproximity coupling device. In some embodiments, the token may transmitthe token data and/or other information after a handshake procedure orthe like with the POS system.

In some embodiments, a token is presented to the proximity couplingdevice by positioning the token within wireless communication range ofthe proximity coupling device. In some embodiments, the token ispresented to the proximity payment device by positioning the token inphysical contact with, and/or by tapping a portion of the token on, theproximity coupling device.

At 512, the method may further include determining the payment accountassociated with the identifier based at least in part on the mapping.

At 514, the method may further include initiating a payment transactionassociated with the payment account. This may include communicating witha payment card system to initiate a payment transaction against thepayment account temporarily associated with the token. In someembodiments, the payment card system includes the processing system 118(FIG. 1).

At 515, the method may further include printing a receipt for thepayment transaction.

At 516, the method may further include initiating a charge forinitiating the payment transaction.

At 518, the method may further include sharing revenue from the chargefor initiating the payment transaction. The revenue may be sharedbetween two or more entities. In some embodiments, the two or moreentities include the venue, the issuer of the token and/or the financialinstitution. In some embodiments, each entity receives a portion of therevenue, the portion being based on one or more services provided bythat entity.

In some embodiments, the method may further include displaying anaccount balance associated with the payment account.

FIG. 5B is a flow chart 520 of a method according to some embodiments.In some embodiments, one or more portions of the method may be performedby a customer, e.g., customer 132A (FIG. 1). In some embodiments, one ormore portions of the method may be performed in association with one ormore token, e.g., token 134A, of the plurality of tokens 134A-134D, thePOS systems 112, 126 the processing system 114 and/or the processingsystem 118 (FIG. 1).

At 522, the method may include receiving the token. In some embodiments,the token comprises the token issued at 504 of the flow chart 500 (FIG.5A).

At 524, the method may further include, after receiving the token,requesting that the token be temporarily associated with a paymentaccount and temporarily usable as a payment token. In some embodiments,the request is made via a website, a telephone, email, mail, in personand/or any other method.

In some embodiments, the method may further include requesting that asecond token be temporarily associated with a payment account andtemporarily usable as a payment token. In some embodiments, the paymentaccount associated with the second token may be the same payment accountas is associated with the first token.

As stated above, in some embodiments, a plurality of the tokens, e.g.,tokens 134A-134B, are issued to a single customer, family and/or agroup, e.g., customer (or family or group) 132A. It may be desirable toassociate two or more tokens, e.g., tokens 134A-134B, of the pluralityof tokens, e.g. tokens 134A-134B, issued to the customer, family and/orgroup, e.g., customer (or family or group) 132A, with the same paymentaccount. In some embodiments, this increases the usefulness (of thetokens) to the family and/or group. In some embodiments two or moretokens, e.g., tokens 134A-134B, of the plurality of tokens, e.g. tokens134A-134B, issued to the customer, family and/or group, e.g., customer(or family or group) 132A, may share a pre-determined amount from thesame payment account. In some embodiments, this further increases theusefulness (of the tokens) to a family and/or group. In someembodiments, the system may be used to limit the amount that a familyand/or group may spend at, and/or in association with, an event and/orattraction, and may also limit their exposure to theft. In someembodiments, this may be particularly helpful if consumption ofalcoholic beverages is expected.

At 526, the method may further include supplying use criteria. In someembodiments, this is performed directly and/or indirectly, by theaccount holder and/or the customer, e.g., customer 132A. In someembodiments, the account holder and/or customer carries this out via awebsite, a telephone, email, mail in person and/or any other method. Insome embodiments, default use criteria is supplied by another entityand/or a processing system.

At 528, the method may further include using the token in a paymenttransaction. In some embodiments, this includes presenting the tokenpresented to the POS system. In some embodiments, a payment transactionis carried out as described above.

In some embodiments, the token may be selectively enabled/disabled inorder to enable and/or disable operation of the token.

FIG. 5C is a flow chart 540 of a method according to some embodiments.In some embodiments, one or more portions of the method may be performedby the financial institution 120 (FIG. 1). In some embodiments, one ormore portions of the method may be performed in association with one ormore token, e.g., token 134A, of the plurality of tokens 134A-134D, thePOS systems 112, 126 and/or the processing system 118 (FIG. 1).

At 542, the method may include receiving a request from a customer totemporarily associate a token issued to the customer with an accountassociated with the customer.

In some embodiments, the account holder and/or customer supplies therequest via a website, a telephone, email, mail, in person and/or anyother method.

At 544, the method may further include temporarily associating the tokenwith the payment account in response at least in part to the request.This may include defining a mapping that associates token data withaccount data.

In some embodiments, the method may further include reporting thetemporary association on a statement for the payment account. In someembodiments, the statement for the payment account is issued to thecustomer.

At 546, the method may further include receiving use criteria. In someembodiments, receiving use criteria comprises receiving the use criteriavia a website, a telephone, and/or mail.

In some embodiments, the use criteria is supplied, directly and/orindirectly, by the account holder and/or customer. In some embodiments,the account holder and/or customer supplies the use criteria via awebsite, a telephone, email, mail, in person and/or any other method.

At 548, the method may further include receiving a request to authorizea payment transaction associated with the payment account. In someembodiments, the payment account is the payment account temporarilyassociated with the token. In some embodiments, the request is suppliedvia a payment card system. In some embodiments, the payment card systemincludes the processing system 118 (FIG. 1).

At 550, the method may further include authorizing the paymenttransaction. In some embodiments, the authorization is supplied via apayment card system. In some embodiments, the payment card systemincludes the processing system 118 (FIG. 1).

At 552, the method may further include initiating a charge forperforming one or more portions of the payment transaction.

At 554, the method may further include sharing revenue from the chargefor performing one or more portions of the payment transaction. Therevenue may be shared between two or more entities. In some embodiments,the two or more entities include the venue, the issuer of the tokenand/or the financial institution. In some embodiments, each entityreceives a portion of the revenue, the portion being based on one ormore services provided by that entity.

At 556, the method may further include reporting the payment transactionon a statement for the payment account.

In accordance with some embodiments, a token may include a body, an RFIDIC and an antenna. The body may comprise a plastic and/or paper materialand may have a generally rectangular card shape. The RFID IC may includecontrol/storage circuitry and transmit/receive circuitry. The RFID ICmay further include contacts. Two of the contacts may be electricallyconnected to the antenna.

FIG. 6 is a block diagram of an architecture 900 according to someembodiments. In some embodiments, one or more of the systems, devicesand/or circuitry (or portion(s) thereof) disclosed herein may have anarchitecture that is the same as and/or similar to one or more portionsof the architecture 900.

Referring to FIG. 6, in accordance with some embodiments, thearchitecture 900 includes a processor 901 operatively coupled to acommunication device 902, an input device 903, an output device 904 anda storage device 906.

In some embodiments, the processor 901 may execute processor-executableprogram code to provide one or more portions of the one or morefunctions disclosed herein and/or to carry out one or more portions ofone or more embodiments of one or more methods disclosed herein. In someembodiments, the processor 901 may be a conventional microprocessor ormicroprocessors.

The communication device 902 may be used to facilitate communicationwith other devices and/or systems. In some embodiments, communicationdevice 902 may be configured with hardware suitable to physicallyinterface with one or more external devices and/or network connections.For example, communication device 902 may comprise an Ethernetconnection to a local area network through which architecture 900 mayreceive and transmit information over the Internet and/or one or moreother network(s).

The input device 903 may comprise, for example, one or more devices usedto input data and/or other information, such as, for example: akeyboard, a keypad, track ball, touchpad, a mouse or other pointingdevice, a microphone, knob or a switch, an infra-red (IR) port, etc. Theoutput device 904 may comprise, for example, one or more devices used tooutput data and/or other information, such as, for example: an IR port,a dock, a display, a speaker, and/or a printer, etc.

The storage device 906 may comprise, for example, one or more storagedevices, such as, for example, magnetic storage devices (e.g., magnetictape and hard disk drives), optical storage devices, and/orsemiconductor memory devices such as Random Access Memory (RAM) devicesand Read Only Memory (ROM) devices.

The storage device 906 may store one or more programs 910-912, which mayinclude one or more instructions to be executed by the processor 901.

In some embodiments, the one or more programs may include one or moreoperating systems, database management systems, other applications,other information files, etc., for operation of the architecture 900.

The storage device 906 may store one or more databases 914-916 and/orcriteria for one or more programs. As used herein a “database” may referto one or more related or unrelated databases. Data and/or otherinformation may be stored in any form. In some embodiments, data and/orother information may be stored in raw, excerpted, summarized and/oranalyzed form.

In some embodiments, one or more portions of one or more embodimentsdisclosed herein may be embodied in a method, an apparatus, a computerprogram product, and/or an article where the article includes a machinereadable storage medium with instructions stored thereon. As usedherein, a machine may be any type of machine. In some embodiments, amachine comprises a computer. In some embodiments, a machine comprises aproximity coupling system.

As used herein, a signal may be any type of signal, i.e., a physicalquantity (e.g., voltage, current, or magnetic field), an indication, amessage and/or any other type of signal or combination thereof.

A wireless communication interface may be any type of wirelesscommunication interface.

A circuit may be programmable or non programmable, general purpose orspecial purpose, dedicated or non dedicated, distributed or nondistributed, shared or not shared, and/or any combination thereof. Ifthe circuit has two or more distributed portions, the two or moreportions may communicate with one another through a communication link.A circuit may include, for example, but is not limited to, hardware,software, firmware, hardwired circuits and/or any combination thereof.

As used herein, a proximity payment device refers to any device, of anyshape, that transmits an account number to a POS system via wirelesstransmission. As used herein, an account number may be numeric, nonnumeric and/or a combination thereof.

In some embodiments, a proximity payment device may also have a contactinterface like that of a conventional smart card that includes a contactinterface.

Unless otherwise stated, terms such as, for example, “in response to”and “based on” mean “in response at least to” and “based at least on”,respectively, so as not to preclude being responsive to and/or based on,more than one thing.

In addition, unless stated otherwise, terms such as, for example,“comprises”, “has”, “includes”, and all forms thereof, are consideredopen-ended, so as not to preclude additional elements and/or features.In addition, unless stated otherwise, terms such as, for example, “a”,“one”, “first”, are considered open-ended, and do not mean “only a”,“only one” and “only a first”, respectively. Moreover, unless statedotherwise, the term “first” does not, by itself, require that there alsobe a “second”.

Although the present invention has been described in connection withspecific exemplary embodiments, it should be understood that variouschanges, substitutions, and alterations apparent to those skilled in theart can be made to the disclosed embodiments without departing from thespirit and scope of the invention as set forth in the appended claims.

1. A method comprising: receiving a request from a customer totemporarily associate a token issued to the customer with a paymentaccount associated with the customer, and temporarily associating thetoken with the payment account in response at least in part to therequest; wherein the temporarily associating the token is performed by aprocessing system.
 2. The method of claim 1, wherein receiving a requestcomprises receiving a request directly from the customer.
 3. The methodof claim 1, wherein the token comprises a ticket to a venue.
 4. Themethod of claim 1, further comprising: reporting the temporaryassociation on a statement for the payment account.
 5. The method ofclaim 1, further comprising: receiving a request to authorize a paymenttransaction associated with the payment account; receiving criteria forusing the token in a payment transaction; determining if the paymenttransaction satisfies the criteria; and authorizing the paymenttransaction if the payment transaction satisfies the criteria.
 6. Themethod of claim 5, wherein the criteria identifies at least one of: agood that may be purchased using the token; and a good that may not bepurchased using the token.
 7. The method of claim 5, wherein the tokencomprises a first token, the method further comprising receiving arequest from the customer to associate a second token with the paymentaccount.
 8. The method of claim 5 wherein the receiving a request toauthorize a payment transaction, the receiving criteria, the determiningand the authorizing are performed by the processing system.
 9. Themethod of claim 5, further comprising reporting the payment transactionon a statement for the payment account.
 10. The method of claim 7,further comprising: receiving criteria for using the second token in apayment transaction; determining if the payment transaction satisfiesthe criteria for using the second token; and authorizing the paymenttransaction if the payment transaction satisfies the criteria for usingthe second token.
 11. The method of claim 10, wherein the criteria forusing the first token in a payment transaction is different than thecriteria for using the second token in a payment transaction.
 12. Themethod of claim 1 wherein temporarily associating the token with thepayment account comprises: associating the token with the paymentaccount for a predetermined time period.
 13. The method of claim 12wherein the predetermined time period is based at least in part on adate of an event at the venue.
 14. A method comprising: issuing a tokento a customer before the token is associated with a payment account; andarranging for the customer to have an ability to request that the tokenbe associated with a payment account and usable as a payment token. 15.The method of claim 14, wherein the token comprises a ticket to a venue.16. The method of claim 15, further comprising: printing a noticeregarding the arrangement.
 17. A method for a processing system, themethod comprising: receiving a mapping associating an identifier of atoken with a payment account; receiving the identifier from a point ofsale system; and determining the payment account based at least in parton the mapping and the identifier received from the point of salesystem.
 18. The method of claim 17, wherein receiving the mappingcomprises: receiving the mapping from a financial institution.
 19. Themethod of claim 17, wherein the token comprises a ticket to a venue. 20.The method of claim 17, further comprising: initiating a paymenttransaction associated with the payment account.
 21. The method of claim17 further comprising: printing a receipt for the payment transaction.22. Apparatus comprising: a processing system to: receive a request froma customer to temporarily associate a token issued to the customer witha payment account associated with the customer, and temporarilyassociate the token with the payment account in response at least inpart to the request.
 23. Apparatus comprising: a processing system to:receive a mapping associating an identifier of a token with a paymentaccount; receive the identifier from a point of sale system; anddetermine the payment account based at least in part on the mapping andthe identifier received from the point of sale system.
 24. An articlecomprising a machine readable storage medium having instructions storedthereon that if executed by a processing system result in the following:receiving a request from a customer to temporarily associate a tokenissued to the customer with a payment account associated with thecustomer, and temporarily associating the token with the payment accountin response at least in part to the request.
 25. An article comprising amachine readable storage medium having instructions stored thereon thatif executed by a processing system result in the following: receiving amapping associating an identifier of a token with a payment account;receiving the identifier from a point of sale system; and determiningthe payment account based at least in part on the mapping and theidentifier received from the point of sale system.